System and method for protecting databases in a hyperconverged infrastructure system

ABSTRACT

A system and method include associating, by a database system of a virtual computing system, a protection schedule with each source database provisioned in the database system, the protection schedule defining a frequency of capturing snapshots and a frequency of capturing transactional logs, capturing, by the database system for each of the source databases, snapshots and transactional logs based upon the frequency of capturing snapshots and the frequency of capturing transactional logs, respectively, and receiving, by the database system, a request identifying a point in time for creating a cloned database from a first source database. The system and method also include retrieving, by the database system, the snapshots and the transactional logs corresponding to the point in time and creating, by the database system, the cloned database by combining data in storage locations identified in the transactional logs and the data in remaining storage locations identified in the snapshots.

BACKGROUND

The following description is provided to assist the understanding of the reader. None of the information provided or references cited is admitted to be prior art.

Virtual computing systems are widely used in a variety of applications. Virtual computing systems include one or more host machines running one or more virtual machines and other entities (e.g., containers) concurrently. Modern virtual computing systems allow several operating systems and several software applications to be safely run at the same time, thereby increasing resource utilization and performance efficiency. However, the present day virtual computing systems have limitations due to their configuration and the way they operate.

SUMMARY

In accordance with some aspects of the present disclosure, a method is disclosed. The method includes associating, by a database system of a virtual computing system, a protection schedule with each source database provisioned in the database system, the protection schedule defining a frequency of capturing snapshots and a frequency of capturing transactional logs, capturing, by the database system for each of the source databases, snapshots and transactional logs based upon the frequency of capturing snapshots and the frequency of capturing transactional logs, respectively, and receiving, by the database system, a request identifying a point in time for creating a cloned database from a first source database. The method also includes retrieving, by the database system, the snapshots and the transactional logs corresponding to the point in time and creating, by the database system, the cloned database by combining data in storage locations identified in the transactional logs and the data in remaining storage locations identified in the snapshots.

In accordance with some other aspects of the present disclosure, another method is disclosed. The method includes receiving, via a dashboard of a database system of a virtual computing system, a request for creating a cloned database from a source database, presenting, by the database system via the dashboard, in response to the request, a time scale for receiving selection of a point in time for creating the cloned database, and retrieving, by the database system, a snapshot and a transactional log of the source database previously captured corresponding to the point in time. The method also includes creating, by the database system, the cloned database by combining data in storage locations identified in the transactional log and the data in remaining storage locations identified in the snapshot, displaying, by the database system, the cloned database within the dashboard, and performing, by the database system, an operation on the cloned database in response to an operation request received via the dashboard.

In accordance with yet other aspects of the present disclosure, a database system of a virtual computing system is disclosed. The database system includes a dashboard, a database storage system for storing a source database and a cloned database, and a database engine for receiving input from and providing output to the dashboard. The database engine is configured to receive a request via the dashboard for creating the cloned database, present via the dashboard and in response to the request, a time scale to receive selection of a point in time, and retrieve a snapshot and a transactional log of the source database previously captured corresponding to the point in time. The database engine is also configured to create the cloned database by combining data in storage locations identified in the transactional log and the data in remaining storage locations identified in the snapshot, display the cloned database within the dashboard, and perform an operation on the cloned database in response to an operation request received via the dashboard.

The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the following drawings and the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example block diagram of a cluster of a virtual computing system, in accordance with some embodiments of the present disclosure.

FIG. 2 is an example block diagram of a database system of the virtual computing system of FIG. 1, in accordance with some embodiments of the present disclosure.

FIG. 3 is an example flowchart outlining operations for provisioning databases by the database system of FIG. 2, in accordance with some embodiments of the present disclosure.

FIGS. 4A-4G are example screenshots showing the operations of FIG. 3 for creating a new database, in accordance with some embodiments of the present disclosure.

FIGS. 5A-5E are example screenshots showing the operations of FIG. 3 for registering an existing database, in accordance with some embodiments of the present disclosure.

FIG. 6 is an example block diagram showing a database protection system of the database system of FIG. 2, in accordance with some embodiments of the present disclosure.

FIGS. 7A-7F are example screenshots showing creating cloned databases from source databases, in accordance with some embodiments of the present disclosure.

FIG. 8 is an example flowchart outlining operations for creating cloned databases using the database protection system of FIG. 6, in accordance with some embodiments of the present disclosure.

FIGS. 9A-9G are example screenshots showing how snapshots and transactional logs are stored within the database system, in accordance with some embodiments of the present disclosure.

FIG. 10 is an example flowchart outlining operations for protecting an external database, in accordance with some embodiments of the present disclosure.

The foregoing and other features of the present disclosure will become apparent from the following description and appended claims, taken in conjunction with the accompanying drawings. Understanding that these drawings depict only several embodiments in accordance with the disclosure and are therefore, not to be considered limiting of its scope, the disclosure will be described with additional specificity and detail through use of the accompanying drawings.

DETAILED DESCRIPTION

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, and designed in a wide variety of different configurations, all of which are explicitly contemplated and made part of this disclosure.

The present disclosure is generally directed to a virtual computing system having a plurality of clusters, with each of the plurality of clusters having a plurality of nodes. Each of the plurality of nodes includes one or more virtual machines and other entities managed by an instance of a monitor such as a hypervisor. These and other components may be part of a datacenter, which may be managed by a user (e.g., an administrator or other authorized personnel). A distributed storage system, for providing storage and protection capabilities, is associated with the virtual computing system. The virtual computing system may be configured for providing database management services. For example, at least some of the one or more virtual machines within the virtual computing system may be configured as database virtual machines for storing one or more databases. These databases may be managed by a database system. The database system may provide a plurality of database services. For example, in some embodiments, the database system may provide database provisioning services and copy data management services.

Database provisioning services involve creating and/or associating databases with the database system for management and use. Creating a new database and associating the database with the database system may be a complex and long drawn process. A user desiring to create a new database with a provider of the database system may make a new database creation request with the database provider. The user request may pass through multiple entities (e.g., people, teams, etc.) of the database provider before a database satisfying the user request may be created. For example, the user may be required to work with a first entity of the database provider to specify the configuration (e.g., database engine type, number of storage disks needed, etc.) of the database that is desired. Upon receiving the database configuration, another entity of the database provider may configure a database virtual machine for hosting the database, while yet another entity may configure the networking settings to facilitate access to the database upon creation. Yet another entity of the database provider may configure database protection services to backup and protect the database. All of these tasks may take a few to several days. Thus, creating the database is a time intensive process and inconvenient for the user. The user may not have the time or desire to wait for the multiple days to create the database.

Further, creating the database using the above procedure requires the user to rely on the other entities. If these other entities become unavailable, the user may have no choice but to wait for those entities to become operational again. Additionally, the user may not be fully privy to or even understand the various configurational details of the desired database that the user may be asked to provide to the other entities for creating the database. The present disclosure provides technical solutions to the above problems. Specifically, the database system of the present disclosure greatly simplifies the database provisioning service. The database system of the present disclosure allows the user to quickly and conveniently create a new database and associate the database with the database system without the need for contacting and working with multiple entities. The entire process of creating and associating the database with the database system may be completed by the user within a span of a few minutes instead of the multiple days mentioned above.

The database system of the present disclosure provides a user friendly, intuitive user interface that solicits information from and conveniently walks the user through the various steps for creating a new database within minutes. The database system may include a catalog of standardized configurations, which the user may select from the user interface for creating the database. The user may modify the standardized configurations or create custom configurations to suit their needs. By virtue of providing standardized configurations, the present disclosure simplifies the database creation process for the user. The user interface also hides the complexity of creating the database from the user. For example, the user need not worry about creating, partitioning, or associating storage space (e.g., storage disk space) with the database that is being created. The user may simply specify a size of the database that is desired in the user interface and the database system automatically translates that size into storage space. Thus, based upon the needs of the user, the user is able to specifically tailor the database during creation and create the database easily and quickly using the user interface.

The database system also provides the ability to register an existing database with the database system. Such existing databases may have been created outside of the database system. Users having existing databases may desire to associate their databases with the database system for management. Similar to creating a new database in the database system, registering an existing database with the database system is easy, convenient, and may be completed within a span of a few minutes via the user interface. As with the creation of a new database, the user interface walks the user through the registration process, provides standardized configurations for the user to select from, ability to modify the standardized configurations, and create new configurations. Upon registering the database with the database system, the database may take advantage of other database management services offered by the database system.

Copy data management services involve protecting a database. Protecting a database means replicating a state of the database for creating a fully functional copy of the database. Replicating the state of the database may involve creating fully functional clones (e.g., back-ups) of the database. Since the clones are fully functional copies of the original or source database, a user may perform operations on the cloned copy that would otherwise be performed on the original database. For example, the user may perform reporting, auditing, testing, data analysis, etc. on the cloned copy of the original database. A cloned database may be created by periodically capturing snapshots of the source database. A snapshot stores the state of the source database at the point in time at which the snapshot is captured. The snapshot is thus a point in time image of the database. The snapshot may include a complete encapsulation of the virtual machine on which the database is created, including the configuration data of the virtual machine, the data stored within the database, and any metadata associated with the virtual machine. Any of a variety of snapshotting techniques may be used. For example, in some embodiments, copy-on-write, redirect-on-write, near-sync, or other snapshotting methods may be used to capture snapshots. From the snapshot, the source database may be recreated to the state at which the snapshot was captured.

However, the number of snapshots that are captured in a given day may be limited. Specifically, because capturing a snapshot requires quiescing (e.g., pausing) the source database and entering a safe mode in which user operations are halted, it is desirable to take only a minimum number of snapshots in a day. Thus, choices of state that may recreated from a snapshot may be limited. If a state is desired that falls between the capture of two snapshots, the user is generally out of luck. Thus, the desire to limit the number of snapshots in a day results in a significant technical problem that results in losing changes made to a database since the last snapshot capture or between two snapshot captures. The present disclosure provides technical solutions to this problem.

Specifically, the present disclosure automatically creates an instance of a database protection system for each database (e.g., source database) that is created within or registered with the database system. The database protection system instance may be configured to protect the source database by automatically capturing snapshots of the source database. Additionally, to avoid losing changes in state between two snapshot captures or since the last snapshot capture, the database system may capture transactional logs. A transactional log may be a text, image, disk, or other type of file that records every transaction or change that occurs on the source database since a last snapshot capture. Thus, by using the snapshots or a combination of snapshots and transactional logs, any state of the source database down to the last second (or even fractions of seconds or other time granularities) may be recreated. Specifically, states of the source database that fall between the capture of two snapshots may be recreated by using a combination of snapshots and transactional logs.

The frequency of capturing transactional logs may be higher than the frequency of capturing snapshots in a day. For example, in some embodiments, by default, a transactional log may be captured every 30 minutes. In other embodiments, the user may define the frequency of capturing transactional logs. Further, since the source database is not quiesced (paused) for capturing the transactional log, user operations may continue while the transactional logs are being captured. Further, since the transactional logs only capture the changes in the database since the last snapshot capture, the transactional logs do not consume a lot of space. Thus, clones of the source database can be created to a point in time by using a combination of transactional logs and snapshots (e.g., between two snapshot captures), or based upon available snapshots (e.g., at the point of snapshot capture).

Further, the frequency with which the snapshots and transactional logs are captured by the database system may depend upon the level of protection desired by the user. The database system may solicit a protection schedule and definition of a Service Level Agreement (“SLA”) from the user. For convenience, the database system may include built-in defaults of the protections schedule and SLA levels that the user may select from. The user may modify the defaults or define new parameters for the protection schedule and SLA. Thus, the level of protection accorded to each database associated with the database system may be individually tailored based upon the requirements of the user. The protection schedule may allow the user to define the frequency of snapshots and transactional logs to be captured each day, and the time-period for capturing daily, weekly, monthly, and/or quarterly snapshots based upon the SLA.

Thus, the present disclosure provides an easy, convenient, cost effective, and user-friendly mechanism for creating and registering databases, as well as effectively protecting those databases.

Referring now to FIG. 1, a cluster 100 of a virtual computing system is shown, in accordance with some embodiments of the present disclosure. The cluster 100 includes a plurality of nodes, such as a first node 105, a second node 110, and a third node 115. Each of the first node 105, the second node 110, and the third node 115 may also be referred to as a “host” or “host machine.” The first node 105 includes database virtual machines (“database VMs”) 120A and 120B (collectively referred to herein as “database VMs 120”), a hypervisor 125 configured to create and run the database VMs, and a controller/service VM 130 configured to manage, route, and otherwise handle workflow requests between the various nodes of the cluster 100. Similarly, the second node 110 includes database VMs 135A and 135B (collectively referred to herein as “database VMs 135”), a hypervisor 140, and a controller/service VM 145, and the third node 115 includes database VMs 150A and 150B (collectively referred to herein as “database VMs 150”), a hypervisor 155, and a controller/service VM 160. The controller/service VM 130, the controller/service VM 145, and the controller/service VM 160 are all connected to a network 165 to facilitate communication between the first node 105, the second node 110, and the third node 115. Although not shown, in some embodiments, the hypervisor 125, the hypervisor 140, and the hypervisor 155 may also be connected to the network 165. Further, although not shown, one or more of the first node 105, the second node 110, and the third node 115 may include one or more containers managed by a monitor (e.g., container engine).

The cluster 100 also includes and/or is associated with a storage pool 170 (also referred to herein as storage sub-system). The storage pool 170 may include network-attached storage 175 and direct-attached storage 180A, 180B, and 180C. The network-attached storage 175 is accessible via the network 165 and, in some embodiments, may include cloud storage 185, as well as a networked storage 190. In contrast to the network-attached storage 175, which is accessible via the network 165, the direct-attached storage 180A, 180B, and 180C includes storage components that are provided internally within each of the first node 105, the second node 110, and the third node 115, respectively, such that each of the first, second, and third nodes may access its respective direct-attached storage without having to access the network 165.

It is to be understood that only certain components of the cluster 100 are shown in FIG. 1. Nevertheless, several other components that are needed or desired in the cluster 100 to perform the functions described herein are contemplated and considered within the scope of the present disclosure.

Although three of the plurality of nodes (e.g., the first node 105, the second node 110, and the third node 115) are shown in the cluster 100, in other embodiments, greater than or fewer than three nodes may be provided within the cluster. Likewise, although only two database VMs (e.g., the database VMs 120, the database VMs 135, the database VMs 150) are shown on each of the first node 105, the second node 110, and the third node 115, in other embodiments, the number of the database VMs on each of the first, second, and third nodes may vary to include other numbers of database VMs. Further, the first node 105, the second node 110, and the third node 115 may have the same number of database VMs (e.g., the database VMs 120, the database VMs 135, the database VMs 150) or different number of database VMs.

In some embodiments, each of the first node 105, the second node 110, and the third node 115 may be a hardware device, such as a server. For example, in some embodiments, one or more of the first node 105, the second node 110, and the third node 115 may be an NX-1000 server, NX-3000 server, NX-6000 server, NX-8000 server, etc. provided by Nutanix, Inc. or server computers from Dell, Inc., Lenovo Group Ltd. or Lenovo PC International, Cisco Systems, Inc., etc. In other embodiments, one or more of the first node 105, the second node 110, or the third node 115 may be another type of hardware device, such as a personal computer, an input/output or peripheral unit such as a printer, or any type of device that is suitable for use as a node within the cluster 100. In some embodiments, the cluster 100 may be part of a data center. Further, one or more of the first node 105, the second node 110, and the third node 115 may be organized in a variety of network topologies. Each of the first node 105, the second node 110, and the third node 115 may also be configured to communicate and share resources with each other via the network 165. For example, in some embodiments, the first node 105, the second node 110, and the third node 115 may communicate and share resources with each other via the controller/service VM 130, the controller/service VM 145, and the controller/service VM 160, and/or the hypervisor 125, the hypervisor 140, and the hypervisor 155.

Also, although not shown, one or more of the first node 105, the second node 110, and the third node 115 may include one or more processing units configured to execute instructions. The instructions may be carried out by a special purpose computer, logic circuits, or hardware circuits of the first node 105, the second node 110, and the third node 115. The processing units may be implemented in hardware, firmware, software, or any combination thereof. The term “execution” is, for example, the process of running an application or the carrying out of the operation called for by an instruction. The instructions may be written using one or more programming language, scripting language, assembly language, etc. The processing units, thus, execute an instruction, meaning that they perform the operations called for by that instruction.

The processing units may be operably coupled to the storage pool 170, as well as with other elements of the first node 105, the second node 110, and the third node 115 to receive, send, and process information, and to control the operations of the underlying first, second, or third node. The processing units may retrieve a set of instructions from the storage pool 170, such as, from a permanent memory device like a read only memory (“ROM”) device and copy the instructions in an executable form to a temporary memory device that is generally some form of random access memory (“RAM”). The ROM and RAM may both be part of the storage pool 170, or in some embodiments, may be separately provisioned from the storage pool. In some embodiments, the processing units may execute instructions without first copying the instructions to the RAM. Further, the processing units may include a single stand-alone processing unit, or a plurality of processing units that use the same or different processing technology.

With respect to the storage pool 170 and particularly with respect to the direct-attached storage 180A, 180B, and 180C, each of the direct-attached storage may include a variety of types of memory devices that are suitable for a virtual computing system. For example, in some embodiments, one or more of the direct-attached storage 180A, 180B, and 180C may include, but is not limited to, any type of RAM, ROM, flash memory, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (“CD”), digital versatile disk (“DVD”), etc.), smart cards, solid state devices, etc. Likewise, the network-attached storage 175 may include any of a variety of network accessible storage (e.g., the cloud storage 185, the networked storage 190, etc.) that is suitable for use within the cluster 100 and accessible via the network 165. The storage pool 170, including the network-attached storage 175 and the direct-attached storage 180A, 180B, and 180C, together form a distributed storage system configured to be accessed by each of the first node 105, the second node 110, and the third node 115 via the network 165, the controller/service VM 130, the controller/service VM 145, the controller/service VM 160, and/or the hypervisor 125, the hypervisor 140, and the hypervisor 155. In some embodiments, the various storage components in the storage pool 170 may be configured as virtual disks for access by the database VMs 120, the database VMs 135, and the database VMs 150.

Each of the database VMs 120, the database VMs 135, the database VMs 150 is a software-based implementation of a computing machine. The database VMs 120, the database VMs 135, the database VMs 150 emulate the functionality of a physical computer. Specifically, the hardware resources, such as processing unit, memory, storage, etc., of the underlying computer (e.g., the first node 105, the second node 110, and the third node 115) are virtualized or transformed by the respective hypervisor 125, the hypervisor 140, and the hypervisor 155, into the underlying support for each of the database VMs 120, the database VMs 135, the database VMs 150 that may run its own operating system and applications on the underlying physical resources just like a real computer. By encapsulating an entire machine, including CPU, memory, operating system, storage devices, and network devices, the database VMs 120, the database VMs 135, the database VMs 150 are compatible with most standard operating systems (e.g. Windows, Linux, etc.), applications, and device drivers.

Thus, each of the hypervisor 125, the hypervisor 140, and the hypervisor 155 is a virtual machine monitor that allows a single physical server computer (e.g., the first node 105, the second node 110, third node 115) to run multiple instances of the database VMs 120, the database VMs 135, and the database VMs 150 with each VM sharing the resources of that one physical server computer, potentially across multiple environments. For example, each of the hypervisor 125, the hypervisor 140, and the hypervisor 155 may allocate memory and other resources to the underlying VMs (e.g., the database VMs 120, the database VMs 135, the database VM 150A, and the database VM 150B) from the storage pool 170 to perform one or more functions.

By running the database VMs 120, the database VMs 135, and the database VMs 150 on each of the first node 105, the second node 110, and the third node 115, respectively, multiple workloads and multiple operating systems may be run on a single piece of underlying hardware computer (e.g., the first node, the second node, and the third node) to increase resource utilization and manage workflow. When new database VMs are created (e.g., installed) on the first node 105, the second node 110, and the third node 115, each of the new database VMs may be configured to be associated with certain hardware resources, software resources, storage resources, and other resources within the cluster 100 to allow those virtual VMs to operate as intended.

The database VMs 120, the database VMs 135, the database VMs 150, and any newly created instances of the database VMs may be controlled and managed by their respective instance of the controller/service VM 130, the controller/service VM 145, and the controller/service VM 160. The controller/service VM 130, the controller/service VM 145, and the controller/service VM 160 are configured to communicate with each other via the network 165 to form a distributed system 195. Each of the controller/service VM 130, the controller/service VM 145, and the controller/service VM 160 may be considered a local management system configured to manage various tasks and operations within the cluster 100. For example, in some embodiments, the local management system may perform various management related tasks on the database VMs 120, the database VMs 135, and the database VMs 150.

The hypervisor 125, the hypervisor 140, and the hypervisor 155 of the first node 105, the second node 110, and the third node 115, respectively, may be configured to run virtualization software, such as, ESXi from VMWare, AHV from Nutanix, Inc., XenServer from Citrix Systems, Inc., etc. The virtualization software on the hypervisor 125, the hypervisor 140, and the hypervisor 155 may be configured for running the database VMs 120, the database VMs 135, the database VM 150A, and the database VM 150B, respectively, and for managing the interactions between those VMs and the underlying hardware of the first node 105, the second node 110, and the third node 115. Each of the controller/service VM 130, the controller/service VM 145, the controller/service VM 160, the hypervisor 125, the hypervisor 140, and the hypervisor 155 may be configured as suitable for use within the cluster 100.

The network 165 may include any of a variety of wired or wireless network channels that may be suitable for use within the cluster 100. For example, in some embodiments, the network 165 may include wired connections, such as an Ethernet connection, one or more twisted pair wires, coaxial cables, fiber optic cables, etc. In other embodiments, the network 165 may include wireless connections, such as microwaves, infrared waves, radio waves, spread spectrum technologies, satellites, etc. The network 165 may also be configured to communicate with another device using cellular networks, local area networks, wide area networks, the Internet, etc. In some embodiments, the network 165 may include a combination of wired and wireless communications. The network 165 may also include or be associated with network interfaces, switches, routers, network cards, and/or other hardware, software, and/or firmware components that may be needed or considered desirable to have in facilitating intercommunication within the cluster 100.

Referring still to FIG. 1, in some embodiments, one of the first node 105, the second node 110, or the third node 115 may be configured as a leader node. The leader node may be configured to monitor and handle requests from other nodes in the cluster 100. For example, a particular database VM (e.g., the database VMs 120, the database VMs 135, or the database VMs 150) may direct an input/output request to the controller/service VM (e.g., the controller/service VM 130, the controller/service VM 145, or the controller/service VM 160, respectively) on the underlying node (e.g., the first node 105, the second node 110, or the third node 115, respectively). Upon receiving the input/output request, that controller/service VM may direct the input/output request the controller/service VM (e.g., one of the controller/service VM 130, the controller/service VM 145, or the controller/service VM 160) of the leader node. In some cases, the controller/service VM that receives the input/output request may itself be on the leader node, in which case, the controller/service VM does not transfer the request, but rather handles the request itself.

The controller/service VM of the leader node may fulfil the input/output request (and/or request another component within/outside the cluster 100 to fulfil that request). Upon fulfilling the input/output request, the controller/service VM of the leader node may send a response back to the controller/service VM of the node from which the request was received, which in turn may pass the response to the database VM that initiated the request. In a similar manner, the leader node may also be configured to receive and handle requests (e.g., user requests) from outside of the cluster 100. If the leader node fails, another leader node may be designated.

Additionally, in some embodiments, although not shown, the cluster 100 may be associated with a central management system that is configured to manage and control the operation of multiple clusters in the virtual computing system. In some embodiments, the central management system may be configured to communicate with the local management systems on each of the controller/service VM 130, the controller/service VM 145, the controller/service VM 160 for controlling the various clusters.

Again, it is to be understood again that only certain components and features of the cluster 100 are shown and described herein. Nevertheless, other components and features that may be needed or desired to perform the functions described herein are contemplated and considered within the scope of the present disclosure. It is also to be understood that the configuration of the various components of the cluster 100 described above is only an example and is not intended to be limiting in any way. Rather, the configuration of those components may vary to perform the functions described herein.

Turning now to FIG. 2, an example block diagram of a database system 200 is shown, in accordance with some embodiments of the present disclosure. FIG. 2 is discussed in conjunction with FIG. 1. The database system 200 or portions thereof may be configured as utility software for creating and implementing database management services. The database system 200 is configured to facilitate creation/registration, querying, and/or administration of the databases associated therewith. Thus, the database system 200 includes a database engine 205 that is configured to receive input from and provide output to a user via a dashboard 210. The database engine 205 is also associated with a database storage system 215 that is configured to store one or more databases under management of the database system 200. In association with the dashboard 210 and the database storage system 215, the database engine 205 is configured to implement one or more database management services of the database system 200. For example, the database engine 205 is configured to provide database provisioning services to create new databases and register existing databases with the database system 200 using a database provisioning system 220. The database engine 205 is also configured to protect databases created or registered by the database provisioning system 220 via a database protection system 225. Although the database provisioning system 220. and the database protection system 225 are shown as separate components, in some embodiments, the database provisioning system and the database protection system may be combined and the combined component may perform the operations of the individual components. The database provisioning system 220 and the database protection system 225 are both discussed in greater detail below.

The database system 200 may be installed on a database VM (e.g., the database VMs 120, the database VMs 135, the database VMs 150 of FIG. 1). The database system 200 may be installed via the controller/service VM (e.g., the controller/service VM 130, the controller/service VM 145, the controller/service VM 160) of the node (e.g., the first node 105, the second node 110, and the third node 115) on which the database system is to be installed. For example, an administrator desiring to install the database system 200 may download a copy on write image file (e.g., qcow or qcow2 image file) on the controller/service VM to define the content and structure of a disk volume to be associated with the database system 200. In some embodiments, instead of a copy on write image file, another type of disk image file, depending upon the type of underlying hypervisor, may be installed. Further, the administrator may create or one or more new database VMs on which the database system 200 is to reside. As part of creating the database VMs, the administrator may allocate a particular number of virtual central processing units (vCPU) to each of the database VMs, define the number of cores that are desired in each vCPU, designate a specific amount of memory to each of the database VMs, and attach a database storage device (e.g., a virtual disk from the storage pool 170) with each of the database VMs. In some embodiments, at least a portion of the database storage device attached to the database system 200 may form the database storage system 215. The administrator may also create a new network interface (e.g., associate a virtual local area network (VLAN), assign an Internet Protocol (“IP”) address to access the database system 200, etc.) with each of the database VMs. The administrator may perform additional and/or other actions to create the database VMs on which the database system 200 resides upon creation and installation of the disk image file.

In some embodiments, the database VMs on which the database system 200 resides may all be located on a single node (e.g., one of the first node 105, the second node 110, and the third node 115). In other embodiments, the database VMs on which the database system 200 resides may be spread across multiple nodes within a single cluster, or possibly amongst multiple clusters. When spread across multiple clusters, each of the associated multiple clusters may be configured to at least indirectly communicate with one another to facilitate operation of the database system 200. Upon installing the database system 200, a user (e.g., the administrator or other user authorized to access the database system) may access the dashboard 210. The dashboard 210, thus, forms the front end of the database system 200 and the database engine 205 and the database storage system 215 form the backend of the database system.

The database system 200 may be accessed via a computing device associated with the virtual computing system 100. In other embodiments, instead of or in addition to being accessible via a particular computing device, the database system 200 may be hosted on a cloud service and may be accessed via the cloud. In some embodiments, the database system 200 may additionally or alternatively be configured as a mobile application suitable for access from a mobile computing device (e.g., a mobile phone). In some embodiments, the database system 200 and particularly the dashboard 210 may be accessed via an Application Programming Interface (“API”) 230. To access the dashboard 210 via the API 230, a user may use designated devices such as laptops, desktops, tablets, mobile devices, other handheld or portable devices, and/or other types of computing devices that are configured to access the API. These devices may be different from the computing device on which the database system 200 is installed.

In some embodiments and when the dashboard 210 is configured for access via the API 230, the user may access the dashboard via a web browser and upon entering a uniform resource locator (“URL”) for the API such as the IP address of the database system 200 or other web address. Using the API 230 and the dashboard 210, the users may then send instructions to the database engine 205 and receive information back from the database engine. In some embodiments, the API 230 may be a representational state transfer (“REST”) type of API. In other embodiments, the API 230 may be any other type of web or other type of API (e.g., ASP.NET) built using any of a variety of technologies, such as Java, .Net, etc., that is capable of accessing the database engine 205 and facilitating communication between the users and the database engine. In some embodiments, the API 230 may be configured to facilitate communication via a hypertext transfer protocol (“HTTP”) or hypertext transfer protocol secure (“HTTPS”) type request. The API 230 may receive an HTTP/HTTPS request and send an HTTP/HTTPS response back. In other embodiments, the API 230 may be configured to facilitate communication using other or additional types of communication protocols. In other embodiments, the database system 200 may be configured for access in other ways.

The dashboard 210 provides a user interface that facilitates human-computer interaction between the users and the database engine 205. The dashboard 210 is configured to receive user inputs from the users via a graphical user interface (“GUI”) and transmit those user inputs to the database engine 205. The dashboard 210 is also configured to receive outputs/information from the database engine 205 and present those outputs/information to the users via the GUI of the management system. The GUI may present a variety of graphical icons, windows, visual indicators, menus, visual widgets, and other indicia to facilitate user interaction. In other embodiments, the dashboard 210 may be configured as other types of user interfaces, including for example, text-based user interfaces and other man-machine interfaces. Thus, the dashboard 210 may be configured in a variety of ways.

Further, the dashboard 210 may be configured to receive user inputs in a variety of ways. For example, the dashboard 210 may be configured to receive the user inputs using input technologies including, but not limited to, a keyboard, a stylus and/or touch screen, a mouse, a track ball, a keypad, a microphone, voice recognition, motion recognition, remote controllers, input ports, one or more buttons, dials, joysticks, etc. that allow an external source, such as the user, to enter information into the database system 200. The dashboard 210 may also be configured to present outputs/information to the users in a variety of ways. For example, the dashboard 210 may be configured to present information to external systems such as users, memory, printers, speakers, etc. Therefore, although not shown, dashboard 210 may be associated with a variety of hardware, software, firmware components, or combinations thereof. Generally speaking, the dashboard 210 may be associated with any type of hardware, software, and/or firmware component that enables the database engine 205 to perform the functions described herein.

Thus, the dashboard receives a user request (e.g., an input) from the user and transmits that user request to the database engine 205. In some embodiments, the user request may be to request a database management service. For example, in some embodiments, the user request may be to request a database provisioning service. In response to the user request for a database provisioning service, the database engine 205 may activate the database provisioning system 220. The database provisioning system 220 includes a database creation system 235 for creating new databases within the database system 200 and a database registration system 240 for registering databases that were previously created outside of the database system with the database system. Although the database creation system 235 and the database registration system 240 are shown as separate components, in some embodiments, those components may be combined together and the combined component may perform the functions of the individual components. The database creation system 235 and the database registration system 240 are discussed in greater detail in FIGS. 3-5E below.

The database protection system 225 is configured to protect databases associated with the database system 200. Thus, the database protection system 225 implements a copy data management service of the database system 200. During creation or registration of a database, the database provisioning system 220 creates an instance of a database protection system 225 for protecting the associated database. Thus, upon the creation or registration of a database, that database may be protected by the associated instance of the database protection system 225 by capturing snapshots, transactional logs, and creating cloned databases. Each instance of the database protection system 225 may receive a variety of user defined constraints in accordance with which the associated database is protected. The database protection system 225 is discussed in greater detail in FIG. 6 below.

The database engine 205, including the database provisioning system 220 and the database protection system 225 may be configured as, and/or operate in association with, hardware, software, firmware, or a combination thereof. Specifically, the database engine 205 may include a processing unit 245 configured to execute instructions for implementing the database management services of the database system 200. In some embodiments, each of the database provisioning system 220 and the database protection system 225 may have their own separate instance of the processing unit 245. The processing unit 245 may be implemented in hardware, firmware, software, or any combination thereof “Executing an instruction” means that the processing unit 245 performs the operations called for by that instruction. The processing unit 245 may retrieve a set of instructions from a memory for execution. For example, in some embodiments, the processing unit 245 may retrieve the instructions from a permanent memory device like a read only memory (ROM) device and copy the instructions in an executable form to a temporary memory device that is generally some form of random access memory (RAM). The ROM and RAM may both be part of the storage pool 170 and/or provisioned separately from the storage pool. In some embodiments, the processing unit 245 may be configured to execute instructions without first copying those instructions to the RAM. The processing unit 245 may be a special purpose computer, and include logic circuits, hardware circuits, etc. to carry out the instructions. The processing unit 245 may include a single stand-alone processing unit, or a plurality of processing units that use the same or different processing technology. The instructions may be written using one or more programming language, scripting language, assembly language, etc.

The database engine 205 may also include a memory 250. The memory 250 may be provisioned from or be associated with the storage pool 170. In some embodiments, the memory 250 may be separate from the storage pool 170. The memory 250 may be any of a variety of volatile and/or non-volatile memories that may be considered suitable for use with the database engine 205. In some embodiments, the memory 250 may be configured to store the instructions that are used by the processing unit 245. Further, although not shown, in some embodiments, the database provisioning system 220 and the database protection system 225 may each, additionally or alternatively, have their own dedicated memory.

Further, the database engine 205 may be configured to handle a variety of types of database engines. For example, in some embodiments, the database engine 205 may be configured to manage PostgreSQL, Oracle, Microsoft SQL server, and MySQL database engines. In other embodiments, the database engine 205 may be configured to manage other or additional database engines. Each database that is created within or registered with the database system 200 may be of a particular “database engine type.” The database engine type may identify the type of database management system (e.g., Oracle, PostgreSQL, etc.) of a particular database. By virtue of creating or registering a database with a particular database engine type, that database is managed in accordance with the rules of that database engine type. Thus, the database engine 205 is configured to be operable with and manage databases associated with a variety of database engine types.

It is to be understood that only some components of the database engine 205 are shown and discussed herein. In other embodiments, the database engine 205 may also include other components that are considered necessary or desirable in implementing the various database management services discussed herein. Similarly, the database provisioning system 220 and the database protection system 225 may have components that are considered necessary or desirable in implementing the various database management services discussed herein.

Referring still to FIG. 2, the database storage system 215 is configured to store one or more databases that are either created within the database system 200 or registered with the database system. The database storage system 215 may include a source database storage 255 and a target database storage 260. The source database storage 255 is configured to store the original instances of the databases (also referred to herein as source databases) that are created within or registered with the database system 200. The target database storage 260 is configured to store the clones of the source databases (also referred to herein as cloned databases). In some embodiments, the source database storage 255 and the target database storage 260 may be provisioned from the storage pool 170 and may include virtual disk storage that is associated with the database VMs (e.g., the database VMs 120, the database VMs 135, the database VMs 150) on which the database system 200, the source databases, and the cloned databases reside. For example, in some embodiments, the source database storage 255 may be associated with one or more database VMs (referred to herein as source database VMs) and the source databases stored within the source database storage may be stored within the virtual disks associated with the source database VMs. Similarly, in some embodiments, the target database storage 260 may be associated with one or more database VMs (referred to herein as target database VMs) and the databases stored within the target database storage may be stored within the virtual disks associated with the target database VMs. In some embodiments, each source database VM may be configured to store one or more source databases and each target database VM may be configured to store one or more target databases. In other embodiments, the source database storage 255 and the target database storage 260 may additionally or alternatively be provisioned from other types of storage associated with the database system 200.

Further, depending upon the size of a particular database and the size of the virtual disk associated with a particular source database VM, a source database may be stored in its entirety on a single source database VM or may span multiple source database VMs. Further, as the size of that source database increases, the source database may be moved to another source database VM, may be stored onto multiple source database VMs, and/or additional storage may be provisioned to the source database VMs to house the increased size of the source database. Similarly, depending upon the size of a cloned database and the size of the virtual disk associated with a particular target database VM, the cloned database may be stored on a single or multiple target database VMs. Further, as the size of the cloned database increases (e.g., by virtue of updating the cloned database to incorporate any changes in the source database), the cloned database may be moved to another target database VM of appropriate size, may be divided amongst multiple target database VMs, and/or additional virtual disk space may be provisioned to the target database VM. Thus, the database storage system 215 is structured with the flexibility to expand and adapt to accommodate databases of various sizes.

The database storage system 215 also includes a database manager 265. In some embodiments, each instance of the source database within the source database storage 255 may include an instance of the database manager 265. In other embodiments, a single instance of the database manager 265 may manage multiple or all source databases. The database manager 265 is configured to work with the database protection system 225 to protect the source databases stored within the source database storage 255. The database manager 265 is discussed in greater detail in FIG. 6 below. Although not shown, the database manager 265 may include a processing unit (e.g., similar to the processing unit 245), a memory (e.g., similar to the memory 250), and other hardware, software, and/or firmware components that are necessary or considered desirable for performing the functions described herein. Further, although the cloned databases in the target database storage 260 are shown as having a database manager, in some embodiments, each cloned database may be associated with a database manager for managing the cloned databases.

Turning now to FIG. 3, an example flow chart outlining operations of a process 300 is shown, in accordance with some embodiments of the present disclosure. The process 300 may include additional, fewer, or different operations, depending on the particular embodiment. The process 300 may be used to implement the database provisioning service. Thus, the process 300 may be used to create a new database or register an existing database. The process 300 is discussed in conjunction with FIGS. 1 and 2 and is implemented by the database provisioning system 220 of the database engine 205 in conjunction with the dashboard 210. Specifically, the database provisioning system 220 receives inputs from the user via the dashboard 210 and performs operations in response to those inputs for creating a new database or registering an existing database. Thus, the process 300 starts at operation 305 with the database provisioning system 220 receiving a user request via the dashboard 210 for either creating a new database or registering an existing database. Specifically, once the database system 200 is installed and the user is able to access the dashboard 210, the dashboard may present an option to create a new database or register an existing database. If the user desires to create a new database, the user may select the database creation option from the dashboard 210 and activate the database creation system 235 of the database provisioning system 220. If the user desires to register an existing database, the user may select the database registration option and activate the database registration system 240 of the database provisioning system 220.

Upon activation, the database creation system 235 or the database registration system 240 may present one or more user interfaces to the user for soliciting parameters for creating a new database or registering an existing database, respectively. For example, at operation 310, the activated one of the database creation system 235 or the database registration system 240 presents, via the dashboard 210, a user interface for requesting the database engine type of the database to be created or registered. The dashboard 210 may present a selection of the database engine types that are supported by the database engine 205. The user may select one of the various database engine types presented on the dashboard 210. As noted above, the database engine type defines the database management system of the database being created or registered. For example, if the user desires to create a database with the database engine type Oracle, and if Oracle is presented as an option on the dashboard at the operation 310, the user may select Oracle on the dashboard. As another example, if the user desires to register an existing database that has been configured with the database engine type Oracle, the user may select Oracle from the dashboards at the operation 310.

The database creation system 235 or the database registration system 240 receives the user's selection of the database engine type at the operation 310. Additionally, the database creation system 235 or the database registration system 240 configures the remaining user interfaces that are presented to the user on the dashboard 210 based on the database engine type selected by the user at the operation 310. For example, if the user selected Oracle as the database engine type at the operation 315, the database creation system 235 or the database registration system 240 may configure the remaining database creation process or the database registration process in accordance with requirements for Oracle. Thus, at operation 315, the database creation system 235 or the database registration system 240 presents one or more user interfaces to the user, via the dashboard 210, for requesting a selection of parameters for defining the configuration for and creating a new source database VM on which the database being created or registered will ultimately reside.

For example, in some embodiments, the activated one of the database creation system 235 or the database registration system 240 may request parameters for defining a software profile, a network profile, a compute profile, and a database parameter profile to be associated with the new source database VM. In other embodiments, the database provisioning system 220 may request other or additional types of parameters from the user for creating the source database VM based upon the database engine type selected at the operation 310. The user interface may present one or more standardized profiles for one or more of the software profile, network profile, compute profile, and database parameter profile. The user may select from the standardized profiles in some embodiments. In some embodiments, the database creation system 235 or the database registration system 240 may also allow the user to modify a standardized profile and/or create new profiles from scratch based upon the user's preferences. Each of the profiles is based upon the database engine type selected at the operation 310. Thus, the standardized profiles that are presented to the user are in compliance with the database engine type. Similarly, the database creation system 235 or the database registration system 240 only allow those changes to the standardized profiles or creation of new profiles that comply with the database engine type.

The software profile defines the software and operating system parameters for the database engine type that is selected at the operation 310. For example, if at the operation 310, the database engine type is selected as PostgreSQL, the software profile may include one or more software and operations system image profiles associated with PostgreSQL. Each software profile may define the rules that are to be applied in managing the database being created or registered. In some embodiments, one or more sample software profiles may be available for the user to select. In other embodiments, the user may create their own custom software profile or modify an existing software profile to suit their needs. When creating their own custom software profile or modifying an existing software profile, in some embodiments, the user may be required to create/modify the software profile before starting the process 300, while in other embodiments, the user may be able to create the custom software profile as part of the operation 315.

The network profile identifies the network location of the database being created or registered to facilitate access to the database after creation or registration. In some embodiments, the network profile may be the same profile that is created during installation of the database system 200. In other embodiments, a different network profile may be used. Similar to the software profile, the database creation system 235 or the database registration system 240 may make a sample network profile available for the user to select. Alternatively, the user may create a new network profile or modify an existing network profile either before starting the process 300 or during the operation 315. The compute profile defines the size/configuration of the source database VM. For example, the compute profile may define the number of vCPUs, number of cores per vCPU, and memory capacity to be associated with the source database VM. In other embodiments, the compute profile may define other or additional configurational parameters. At the operation 315, the database creation system 235 or the database registration system 240 may also request the database parameter profile from the user. The database parameter profile defines the custom parameters that are applied to the database being created or registered. Again, the database creation system 235 or the database registration system 240 may make sample compute profiles and/or a sample database parameter profiles available for the user to select in some embodiments. Alternatively, the user may create custom compute and/or database parameter profiles or modify existing compute and/or database parameter profiles, either before starting the process 300 or during the operation 315.

In some embodiments, the database creation system 235 or the database registration system 240 may pre-select a default option for the user for one or more of the software profile, compute profile, network profile, and the database parameter profile. The database creation system 235 or the database registration system 240 may allow the user to change the default options by selecting another standardized option, modifying a standardized option, or creating a new profile. Thus, at the operation 315, the database creation system 235 or the database registration system 240 receives selection of the various parameters for creating a new source database VM.

In some embodiments, based upon the parameters received from the user, the database creation system 235 or the database registration system 240 may create a new source database VM at the operation 315. In other embodiments, the database creation system 235 or the database registration system 240 may wait until other remaining parameters are received before creating the source database VM. In some embodiments, instead of creating a new source VM, the database creation system 235 or the database registration system 240 may allow the user to use a previously created source database VM. Thus, at the operation 315, the database creation system 235 or the database registration system 240 may first request the user to select one option from either creating a new source database VM or using an existing (e.g., previously created) source database VM. Based on the user's selection, the database creation system 235 or the database registration system 240 may request the various profiles discussed above or request the user to identify the existing source database VM to use. In some embodiments, the database creation system 235 or the database registration system 240 may present a list of existing source database VMs created previously for the database engine type selected at the operation 310 and that have space available to receive the database being created or registered. The user may select one source database VM from the list. The database creation system 235 or the database registration system 240 may facilitate the user selection of an existing source database VM in other manners (e.g., by allowing the user to browse to a location, etc.).

Upon receiving selection of the various profiles for creating a new source database VM or receiving selection of an existing source database VM, at operation 320, the database creation system 235 or the database registration system 240 presents one or more user interfaces, via the dashboard 210, for requesting parameters (e.g., configurational details) for the database being created/registered. For example, the database creation system 235 or the database registration system 240 may request a database name and a description of the database being created or registered to distinguish that database from other databases within the database system 200. The database creation system 235 or the database registration system 240 may also request a database password to restrict access to the database to only authorized users, a database size to determine how much storage space is needed for storing that base, and/or any additional or other parameters that may be considered necessary or desirable in creating/registering the database. Further, the parameters that are requested may vary based upon whether a database is being created or whether an existing database is being registered. For example, if an existing database is being registered, the database registration system 240 may automatically determine the size of the database. In some embodiments, certain default values may be pre-selected for the user and the user may be allowed to change those values. Thus, at the operation 320, the database creation system 235 or the database registration system 240 receives selection of parameters from the user, via the dashboard 210, for either creating a new database or registering an existing database.

At operation 325, the database creation system 235 or the database registration system 240 presents one or more user interfaces, via the dashboard 210, to request selection of parameters for creating an instance of a database protection system (e.g., the database protection system 225) for the database being created or registered by the process 300. The instance of the database protection system is configured to protect the database being created or registered by the process 300. To create the instance of the database protection system, the database creation system 235 or the database registration system 240 may request a name and description for the instance of the database protection system 225, a level of a Service Level Agreement (“SLA”), and a protection schedule to define rules based on which the instance of the database protection system 225 operates.

An SLA is an agreement between a service provider (e.g., the owner of the database system 200) and the user (e.g., the owner of the database) that outlines, among other things, the protection scope of the database. The protection scope defines for how long data from the database being created or registered is retained. Thus, the protection scope defines the database retention policy. In some embodiments, the SLA may define various protection parameters such as continuous, daily, weekly, monthly, quarterly, or yearly protection parameters for determining the protection scope of the database being created/registered. In other embodiments, the SLA may define other or additional protection parameters.

Each database for which an instance of the database protection system 225 is created may be protected by capturing snapshots and/or transactional logs. The number of snapshots and transactional logs to be captured on each day may be defined by the user in the protection schedule. As used herein, a “day” may be any 24-hour period (e.g., from midnight to Noon). In some embodiments, the protection schedule may define default values to define the frequency of capturing snapshots and transactional logs, which the user may modify. Thus, based upon the frequency of capturing snapshots and transactional logs defined in the protection schedule, the instance of the database protection system 225 may be configured to capture one or more snapshots and one or more transactional logs each day. Generally speaking, the number of transactional logs that are captured each day may be higher than the number of snapshots that are captured on that day. Since it is impractical and expensive to indefinitely store the captured snapshots and the transactional logs, the protection parameters in the SLA define the duration for how long those snapshots and transactional logs are stored.

For example, the continuous protection parameter within the SLA defines the duration in days for which all captured snapshots and transactional logs are retained. For example, if the continuous protection parameter is defined as 30 days, the instance of the database protection system 225 is configured to retain all snapshots and transactional logs that are captured within the last 30 days. By retaining all snapshots and the transactional logs, the user may replicate any or substantially any state of the database (down to a second or even a fraction of a second).

The SLA may also define a daily protection parameter, which defines the duration in days for which a daily snapshot is stored. For example, if the daily protection parameter is 90 days, the instance of the database protection system 225 is configured to store a daily snapshot for 90 days. The protection schedule may define the time of day to identify the snapshot that is designated as the daily snapshot. For example, if the user specifies that the snapshot captured at 11:00 AM every day is the daily snapshot and the SLA defines the daily protection parameter for 90 days, the instance of the database protection system 225 may be configured to store a daily snapshot that was captured at or closest to 11:00 AM and store the daily snapshot for 90 days.

Similarly, the SLA may define weekly, monthly, and quarterly protection parameters. A weekly protection parameter in the SLA may define the duration in weeks for which a weekly snapshot is stored. The protection schedule may define the day of the week to identify which snapshot is designated as the weekly snapshot. For example, if the user defines in the protection schedule that the snapshot captured on Monday is to be designated as the weekly snapshot, and the weekly protection parameter in the SLA specifies a duration of 8 weeks, the instance of the database protection system 225 may store the snapshot captured every week on Monday for 8 weeks. If multiple snapshots are captured each day, the protection schedule may also define which snapshot captured on the designated day of the week (e.g., Monday) serves as the weekly snapshot. In some embodiments, the time defined in the protection schedule for capturing a daily snapshot may be used. For example, if the protection schedule defines that the snapshot captured at 11:00 AM is the daily snapshot, and the weekly snapshot is to be captured on Monday, the instance of the database protection system 225 may store the snapshot captured at or closest to 11:00 AM every Monday as the weekly snapshot. In other embodiments, another time period may be used.

Likewise, a monthly protection parameter in the SLA may define a duration in months for which a monthly snapshot is to be stored. The user may specify the date within the protection schedule for identifying which snapshot corresponds to the monthly snapshot. For example, the user may specify storing the snapshot captured on the 20^(th) of every month as the monthly snapshot in the protection schedule, and the monthly protection parameter may specify a duration of 12 months for storing the monthly snapshot. Thus, the instance of the database protection system 225 stores a monthly snapshot captured on the 20^(th) of every month and stores that monthly snapshot for 12 months. A quarterly protection parameter in the SLA may define a duration in quarters for which a quarterly snapshot is to be stored and the user may specify in the protection schedule which months correspond to the various quarters. For example, the user may specify January, April, July, and October as the quarters and the quarterly protection parameter may specify storing the quarterly snapshots for 20 quarters. Thus, the instance of the database protection system 225 may designate a snapshot captured on the first day of January, April, July, and October (e.g., January 1, April 1, July 1, and October 1) as the quarterly snapshot and store the quarterly snapshot for 20 quarters.

Thus, for each protection parameter that is defined in the SLA, a corresponding value may be requested from the user in the protection schedule to identify which snapshot corresponds to that protection parameter. It is to be understood that the various protection parameters and their respective schedules mentioned above are only examples and may vary from one embodiment to another as desired. Further, when the duration specified by a protection parameter expires, any snapshots or transactional logs that are expired (e.g., past their duration) may be deleted. As an example, if a snapshot is to be stored for 30 days, on the 31^(st) day, that snapshot may be deleted. Thus, each snapshot and transactional log is managed based on the SLA and protection schedule independent from other snapshots and transactional logs.

Additionally, to simplify user selection, in some embodiments, various levels of SLA may be pre-defined within the database provisioning system 220. Each level of the SLA may have default values of the various protection parameters. For example, in some embodiments, the various levels of SLA may be GOLD, SILVER, BRONZE and the various protection parameters for these levels may be as follows:

Name Continuous Daily Weekly Monthly Quarterly GOLD 30 Days 90 Days 16 Weeks 12 Months 75 Quarters  SILVER 14 Days 60 Days 12 Weeks 12 Months 0 Quarters BRONZE  7 Days 30 Days  8 Weeks  6 Months 0 Quarters

It is to be understood that the nomenclature of the GOLD, SILVER, BRONZE levels of the SLA is only an example and the levels may be given different names in other embodiments. Further, although three levels of the SLA are described herein, in other embodiments, greater or fewer than three SLA levels may be used. Additionally, the values of the protection parameters in each level of the SLA may vary from one embodiment to another. The database creation system 235 or the database registration system 240 may present the various pre-defined SLA levels to the user at the operation 325 to select from. In some embodiments, the database creation system 235 or the database registration system 240 may allow the user to modify the values of one or more protection parameters in the pre-defined SLA levels. For example, if the user desires to select the GOLD level, but would like continuous protection for 45 days instead of the default value of 30 days shown in the table above, the user may modify the continuous protection parameter of the GOLD level. Thus, the pre-defined SLA levels provide the convenience and flexibility of tailoring the various protection parameters to suit the user's needs. Alternatively, the database creation system 235 or the database registration system 240 may allow the user to create a new SLA at the operation 325.

To create a new SLA, upon receiving input from the user at the operation 325 indicating creation of a new SLA, the database creation system 235 or the database registration system 240 may present one or more user interfaces to the user requesting certain information. For example, the database creation system 235 or the database registration system 240 may request an SLA name, description, and values for the continuous, daily, weekly, monthly, and quarterly protection parameters. The database creation system 235 or the database registration system 240 may request other or additional details as well. Upon receiving the various inputs from the user for creating the new SLA, the database creation system 235 or the database registration system 240 may create the new SLA and allow the user to select that SLA at the operation 325.

Therefore, at the operation 325, the database creation system 235 or the database registration system 240 receives selection of the SLA and the protection schedule for creating an instance of the database protection system 225 for the database being created/registered. At operation 330, upon receiving the various user selections at the operations 310-325, the database creation system 235 or the database registration system 240 creates a new database or registers the existing database with the database system 200. To create/register the database, the database creation system 235 or the database registration system 240 initiates a series of operations. For example, the database creation system 235 or the database registration system 240 may create a source database VM (or designate an existing source database VM), convert the database size into a number of virtual disks that are needed to house the database, create a database profile having a database name, description, network information, etc., attach the software and parameters of the database engine type with the database, create an instance of the database protection system, associate the SLA and schedule with the database protection system, designate storage for storing snapshots and transactional logs, etc. Once the database is created/registered, database management services may be applied to the database.

In some embodiments, the database creation system 235 or the database registration system 240 may request other or additional information for creating/registering the database. For example, the database creation system 235 or the database registration system 240 may request which cluster or clusters the user desires to create/register the database, which node or nodes on a cluster the user desires to create the source database VM, etc. Thus, the database system 200 provides an easy, convenient, and flexible mechanism to create a new database or register an existing database using a user friendly and intuitive user interface. Instead of requiring multiple days to create/register a database, using the user interface of the present disclosure, the database may be created/registered within minutes. Once created/registered, additional database management services may be implemented on those databases.

Turning now to FIGS. 4A-5E, example user interfaces for creating and registering a database are shown, in accordance with some embodiments of the present disclosure. FIGS. 4A-4G show example user interfaces for creating a database, while FIGS. 5A-5E show example user interfaces for registering a database. FIGS. 4A-5E are discussed in conjunction with FIGS. 1-3. Referring to FIGS. 4A-4G, FIG. 4A shows an example dashboard 400. The dashboard 400 is similar to the dashboard 210. The dashboard 400 becomes accessible to the user upon installing the database system 200 and allows the user to manage and monitor activities across multiple databases that are created/registered within the database system. In some embodiments, the user may be required to be authenticated before being able to access the dashboard 400.

The dashboard 400 may include a toolbar 405 and a body 410. The toolbar 405 is configured to switch between various control functions of the database system 200. In some embodiments, the toolbar 410 includes a main menu 415, an alerts menu 420, and a user view menu 425. The main menu 415 may be configured as a drop-down list that enables the user selected within the user view menu 425 to select and activate a control function. For example, when the control function “dashboard” is selected in the main menu 415, the dashboard 400 may be configured to display a “home page” 430 in the body 410 of the dashboard. As the control function selected in the main menu 415 is changed, the page (or at least portions thereof) that is displayed in the body 410 of the dashboard 400 may change to reflect the control function that is activated. The alerts menu 420 allows the user to view and monitor any alerts that are occurring within the database system. An “alert” may be indicative of an error or issue in the database system that needs user attention. In some embodiments, alerts may be color coded to identify the criticality of the alert. The user view menu 425 determines which features are accessible to a particular user. For example, if the user selected in the user view menu 425 is an administrator, certain features that are generally not available to a non-administrator user may be activated. It is to be understood that the toolbar 405 is only an example and may vary from one embodiment to another.

The homepage 430 displayed within the body 410 provides a summary or a “quick-glance” view of all the databases (e.g., source databases) that are managed by the database system 200. The homepage 430 may be divided into one or more components or cells. For example, the homepage 430 may include a database list cell 435A that lists all of the source databases stored in the source database VMs of the database system 200 and provides a summary of each of those source databases (e.g., name of the source database, database engine type, size of the database, name of the instance of the database protection system, number of cloned databases created from the source database, etc.). A summary cell 435B lists the total number of source databases created or registered on the source database VMs combined (e.g., the total number of databases listed in the database list cell 435A), the total number of cloned databases created from those total number of source databases, data usage values of the source and/or the cloned databases, etc. A clone cell 435C provides history on the cloning of the databases (e.g., number of clones created in a given time period, whether the cloning was successful or not, etc.). A version cell 435D provides information on the cluster on which the source databases resides and the version of the software implemented by the database system. An alerts cell 435E provides additional details on the various alerts being generated by the databases listed within the database list cell 4335A.

It is to be understood that the various components or cells of the homepage 430 shown in FIG. 4A are examples and features thereof may vary from one embodiment to another. For example, the number of components or cells that are shown on the homepage 430 may vary from one embodiment to another. Likewise, the details that are displayed within each component or cell may vary from one embodiment to another. The orientation, placement, size, and other design aspects of each component or cell may vary from one embodiment to another. In some embodiments, the configuration of the homepage 430 and/or the configuration of each component/cell may be defined by the user by using a settings menu option of the dashboard 400. By virtue of the dashboard 400, the user may get a quick glance summary of the various source databases that are managed by the database system 200, as well as a quick summary of the configuration and specifics of each source database. Via the dashboard 400, the user may also decide to perform various database management services on the source databases.

For example, to initiate a database provisioning service, the user authorized to request the database provisioning service may select a “databases” option from the main menu 415 to display a database page 440 (shown in FIG. 4B) in the body 410 of the dashboard. If the user selected in the user view menu 425 is not permitted to request the database provisioning service, the “databases” option may be inactivated or not shown in the main menu 415. The database page 440 may display a database menu 445A from which the user may view additional information and/or perform additional operations. The database page 440 may also include a database detail component 445B to display additional details corresponding to the option selected from the database menu 445A. For example, as shown in FIG. 4B. upon selecting the “Sources” option from the database menu 445, a list of the source databases associated with the database system 200 may be displayed within the database detail component 445B. The user may select any one of the source databases to view additional details of that source database and/or perform permitted operations on that source database.

The database page 440 may also allow the user to create a new database or register an existing database. For example, the user may select a create button 445C on the database page 440 to send a user request to the database engine 205 to start the process 300 for creating a new database. Likewise, the user may select a register button 445D to initiate a registration process and sending a user request to the database engine 205.

Upon selecting the create button 445C, the database engine 205, and particularly the database creation system 235 of the database engine may present a user interface 450, shown in FIG. 4C. The user interface 450 identifies the various steps of creating the new database and highlights the current step. For example, the user interface 450 has the “Engine” step highlighted. By virtue of identifying the various steps of creating the new database, the dashboard 400 keeps the user informed as to which step the database creation process is on and which steps are coming up next. The user interface 450 may also present one or more database engine types that are supported by the database system 200. The user may select one of the database engine types to highlight the selection. For example, the PostgreSQL database engine type is shown selected in the user interface 450. The user may select the “Next” button to send the selected database engine type selection to the database creation system 235, which in response, presents a user interface 455 of FIG. 4D.

The user interface 455 identifies that the database creation process is at the “Server” step for creating a new source database VM or identifying an existing source database VM. The user interface 455 may, thus, allow a user to select an option 455A to create a new source database VM or an option 455B to use an existing source database VM. In the user interface 455 of FIG. 4D, the option 455A for creating a new source database VM is shown selected. Thus, the user interface 455 requests user selection of one or more profiles for creating a new source database VM. For example, the user interface 455 may request a name 455C for the source database VM, a software profile 455D, a compute profile 455E, a network profile 455F, a description 455G for the source database VM, and security options 455H for the source database VM. The user interface 455 may also request a parameter profile for the source database VM. In other embodiments, the user interface 455 may request additional or other information for creating a new source database VM.

Although not shown, if the user selects the option 455B for using an existing source database VM, the user interface 455 may display options for allowing the user to identify an existing source database VM. Upon selecting the “Next” button, the various user selections of the user interface 455 are sent to the database creation system 235, which then presents a user interface 460 of FIG. 4E to the user on the dashboard 400.

The user interface 460 identifies that the database creation process is at the “Database” step at which various parameters for creating a database on the source database VM are received from the user. The user interface 460 also requests the user to provide a name 460A and description 460B for the database being created, a password 460C and 460D to restrict access to the database, a size 460E of the database to be created, a database parameter profile 460F to be applied to the database and the source database VM, a listener port 460G for the database engine type selected in the user interface 450, and any other details (e.g., details 460H) that may be needed or considered desirable to have in creating the database. When the user is satisfied with the selections on the user interface 460, the user may select a “Next” button to send the selections to the database creation system 235. The database creation system 235 may then present a user interface 465 of FIG. 4F.

The user interface 465 identifies that the database creation process is at the last step of creating the “Time Machine.” The user interface 465 is configured to request selection of SLA and protection schedule from the user for creating an instance of the database protection system 225. The user interface 465, thus, requests a name 465A and description for the instance of the database protection system 225, an SLA level 465C, and a protection schedule 465D. Within the protection schedule 465D, the user interface 465 requests the user to provide a number of snapshots 465E desired each day, a number of transactional logs 465F desired each day, and time periods 465G for identifying which snapshot to designate as the daily snapshot, 465H for identifying which snapshot to designate as the weekly snapshot, 465I for identifying which snapshot to designate as the monthly snapshot, and 465J for identifying which snapshot to designate as the quarterly snapshot. Upon providing the various parameters in the user interface 465, the user may select a “Next” button to send the selections to the database creation system 235 and start the database creation. The database creation system 235 may display a status of the database creation in a user interface 470 of FIG. 4G.

Upon creating the database, the newly created database may be displayed within the database list cell 435A, within the database page 440, and anywhere else where source databases are listed. The database creation system 235 may also update the various calculations and numbers in the dashboard 400 that provide some statistic of the source databases (e.g., the summary cell 435B). It is to be understood that the configurations of the various user interfaces of FIGS. 4A-4G may vary from one embodiment to another. For example, the various selections may be displayed as drop-lists, as radio buttons, or in other ways. Similarly, some fields may be pre-filled with default values and allowed to be changed by the user if desired. The placement of the various fields, the size, orientation, and other design aspects of those fields may be varied as well. Additionally, some fields may be considered mandatory, while other fields may be designated as mandatory to be filled in by the user. The dashboard 400 thus provides an easy mechanism for creating a new database in a simple, user friendly, and intuitive user interface.

Turning now to FIGS. 5A-5E, example user interfaces for registering an existing database are shown, in accordance with some embodiments of the present disclosure. Similar to the database creation process, the database registration process is initiated from a dashboard 500. The dashboard 500 is similar to the dashboards 210 and 400. The dashboard 500 includes a database page 505, which is similar to the database page 440. To register an existing database, the user may select a register button 510 and select “Next.” Upon selecting “Next,” the database registration system 240 may be activated, which starts the database registration process by displaying a user interface 515 of FIG. 5B. From the user interface 515, the user may select the desired database engine type and select “Next.” Upon selecting “Next,” the user's selection of the database engine type is sent to the database registration system 240, which then displays a user interface 520 of FIG. 5C.

By way of the user interface 520, the database registration system 240 requests the user for creating a new source database VM or selecting an existing source database VM. Likewise, by way of user interface 525 of FIG. 5D, the database registration system 240 requests the user for providing various parameters of the existing database, and by way of user interface 530, the database registration system requests the user to define the SLA and protection schedule. Upon receiving all of the parameters from the user, the database registration system 240 registers the database. Similar to the user interface 470, the database registration system may display the registration status in a user interface. Upon registration, the database becomes a source database that resides on a source database VM and on which other database management services may be applied.

Referring now to FIG. 6, an example block diagram of a database system 600 is shown, in accordance with some embodiments of the present disclosure. The database system 600 is similar to the database system 200. Therefore, the components of the database system 600 that are already discussed with respect to the database system 200 are not discussed again. The database system 600 includes a database engine 605 that is associated with a dashboard 610 via an API 615. The database engine 605 is also associated with a database storage system 620 for storing one or more databases managed by the database system 600. The database engine 605 is similar to the database engine 205, the dashboard 610 is similar to the dashboard 210, the API 615 is similar to the API 230, and the database storage system 620 is similar to the database storage system 215. The database engine 605 includes a database protection system 625 that is configured to protect databases that are associated with the database system 600. The database protection system 625 is similar to the database protection system 225. Although not shown, the database engine 605 also includes a database provisioning system similar to the database provisioning system 220.

As discussed above, an instance of the database protection system 625 may be created for each source database when that source database is created or registered within the database system 600. Thus, the database protection system 625 may include multiple instances of the database protection system—one for each source database. For example, the database protection system 625 may include database protection system instance 630A-630N (collectively referred to herein as database protection system instances 630). In other embodiments, each instance of the database protection system (e.g., the database protection system instances 630A-630N) may be configured to protect more than one source database. Each of the database protection system instances 630A-6930N may respectively include a clone management system 635A-635N (collectively referred to herein as clone management systems 635) and a snapshot/log capturing system 640A-640N (collectively referred to herein as snapshot/log capturing systems 640).

Each of the database protection system instances 630 may be associated with a source database stored within a source database storage 645. The source database storage 645 is similar to the source database storage 255. Thus for example, the database protection system instance 630A may be associated with a source database 650A stored within the source database storage 645, the database protection system instance 630B may be associated with a source database 650B of the source database storage, the database protection system instance 630N may be associated with a source database 650N, and so on. Thus, the clone management system 635A and the snapshot/log capturing system 640A of the database protection system instance 630A may be configured to protect the source database 650A, the clone management system 635B and the snapshot/log capturing system 640B may be configured to protect the source database 650B, the clone management system 635N and the snapshot/log capturing system 640N may be configured to protect the source database 650N, and so on. By virtue of having the database protection system instances 630 for each of the source databases 650A-650N (collectively referred to herein as the source databases 650), the protection of each of those databases may be customized and tailored to suit the user's needs.

To protect the source databases 650, the database protection system instances 630 may create a clone of those source databases. The clones of the source databases 650 (e.g., cloned databases) may be stored within a target database storage 655. The target database storage 655 is similar to the target database storage 260. For each source database (e.g., the source databases 650) that is stored within the source database storage 645, one or more clones of that source database may be created and stored within the target database storage 655. For example, when a clone of the source database 650A is created, a cloned database 660A is created and stored within the target database storage 655. Similarly, clones of the source databases 650B and 650N may be created as cloned databases 660B and 660N, respectively, and stored within the target database storage 655. The cloned databases 660A-660N are collectively referred to herein as the cloned databases 660. Although each of the source databases 650 in the source database storage 645 has been shown as having a corresponding instance of the cloned databases 660 in the target database storage 655, it is to be understood that in some embodiments, clones of only some of the source databases stored in the source database storage may be made. The source databases 650 that have not been cloned may not have a cloned database within the target database storage 655.

Further, similar to the source databases 650, which reside on a database VM (e.g., the source database VMs), the cloned databases 660 also reside on a database VM. The database VMs on which the cloned databases 660 reside are referred to herein as target database VM. Each of the cloned databases 660 may reside entirely on one target database VM or may span across multiple target database VMs. In some embodiments, the source database VMs and the target database VMs may be created on the same node or different nodes of the same cluster or across multiple clusters.

Thus, the database protection system instances 630, and particularly the clone management systems 635 of the database protection system instances creates the cloned databases 660 from the source databases 650 stored within the source database storage 645, and stores the cloned databases within the target database storage 655. The cloned databases 660 may be of a variety of types. As discussed above, each of the source databases 650 are created or registered on a source database VM. Thus, each of the cloned databases 660 may include a clone of the source database VM only (e.g., to create the target database VM) or may include the clone of the source database VM plus the database that resides on that source database VM. For example, the cloned database 660A of the source database 650A may include a clone of the source database VM on which the source database 650A resides or a clone of that source database VM plus the database 650A. When both the source database VM and the source database 650A are cloned, the cloned database 660A may include a target database VM created on the target database storage 655 with a similar or different configuration as the source database VM and the clone of the source database stored on the target database VM. When only the source database VM is cloned, a target database VM is created for that source database VM and stored on the target database storage 655. The target database VM may be used at a later point to store the clone of the source database that resides on the associated source database VM. Thus, the cloned databases 660 may include the source database VM only, the source database VM plus the source database, or the source database only (which is to be stored on a previously created target database VM).

The cloned databases 660 may be considered operationally same (or substantially similar) to the source databases 650. Each of the cloned databases 660 may be refreshed/updated to incorporate any changes that may have occurred in the source databases 650 since the cloned databases were created. In some embodiments, the operations that are performed on the source databases 650 may be performed on the cloned databases 660 as well. Thus, in some embodiments, instead of using the source databases 650, the cloned databases 660 may be used for performing operations (e.g., analyzing data). The cloned databases 660 may be created from snapshots and transactional logs captured from the source databases 650. The cloned databases 660 are generally created upon receiving a user request. The user may request to clone a particular one of the source databases 650 to a point in time or to a specific snapshot. For example, the user may request a cloned database of a particular one of the source databases 650 as that source database existed at 11:00 AM on a particular date. Alternatively, the user may specifically identify a snapshot and request a cloned database of the source databases 650 based on that snapshot. Creating a cloned database (e.g., the cloned databases 600) involves replicating a state of the source databases 650. The “state” of the source databases 650 may include the configuration of the source database, the user data stored within the source database, metadata stored within the source database, and any other information associated with the source database. In other words, a cloned database may be an exact or substantially exact copy of the source database.

Thus, upon receiving a user request to create a cloned database (e.g., the cloned database 660A) from a source database (e.g., the source database 650A), the clone management system (e.g., the clone management system 635A) associated with the source database may retrieve snapshots and transactional logs of the source database from a repository where the snapshots and transactional logs are stored. If the user request is to clone the source database to a point in time, the clone management system (e.g., the clone management system 635A) may retrieve all snapshots and transactional logs captured of the source database at that point in time and create a cloned database (e.g., the cloned database 660A) from those snapshots and transactional logs. The cloned database (e.g., the cloned database 660A) represents the state of the source database at the requested point in time. If the user request is to clone the source database based on a particular available snapshot, the clone management system (e.g., the clone management system 635A) may retrieve that particular snapshot and create a cloned database (e.g., the cloned database 660A) from that particular snapshot. The cloned database (e.g., the cloned database 660A) represents the state of the source database (e.g., the source database 650A) at the time the requested snapshot was captured. Thus, the clone management systems 635 are configured to create the cloned databases 660. The clone management systems 635 are also configured to refresh the cloned databases 660, as well as manage/perform any operations performed on the cloned databases.

Referring now to FIGS. 7A-7F in conjunction with FIGS. 6 and 4A, example user screenshots illustrating the cloning of a source database are shown, in accordance with some embodiments of the present disclosure. To clone a source database, the user may start from dashboard 700 of FIG. 7A. The dashboard 700 is similar to the dashboard 400. To create a clone of a source database, the user may select the option “time machines” from main menu 705. Upon selecting the option “time machines” from the main menu 705, the user may select a particular source database to be cloned. Alternatively, in some embodiments, the user may first select the source database to be cloned and then select the option “time machines” from the main menu 705. Upon selecting the source database to be cloned, the database protection system instance associated with the source database is activated. Further, the database protection system instance displays, in a body 710 of the dashboard 700, a summary section 715. The summary section 715 may display one or more configurational features of the source database such as the database engine type (e.g., type in FIG. 7A), how long ago was the source database created (e.g., age), the last time the source database was updated (e.g., last update), the next period for capturing a transactional log (e.g., next log catch up), name of the source database (e.g., name), the number of clones previously made of the source database (e.g., clones), the SLA level of the source database (e.g., SLA), and the protection schedule (e.g., schedule). In other embodiments, other or additional details may be provided in the summary section 715.

The database protection system instance may also display within the body 410 a menu section 720 that provides options of operations that the user may perform on the source database. For example, the user may select a clone option 725A to create a new clone of the source database. The user may elect to manually capture transactional logs or snapshots by interacting with log catch up option 725B and snapshot option 725C, respectively. Similarly, the user may perform other operations by selecting another one of options 725D. Depending upon the options that the user is authorized to make, some of the options 725A-725D may be inactivated. Further, although specific options are shown in FIG. 7A, the number and types of options may vary from one embodiment to another. The database protection system instance may also display a calendar 730 visually representing the SLA associated with the source database. For example, the calendar 730 may include a color coded legend to represent the duration for the continuous, daily, weekly, monthly, and quarterly protection parameters for a selected number of months. For example, the calendar 730 of FIG. 7A shows five months (May-September) with dates highlighted based upon the protection parameter that applies to that date.

For example, by looking at the calendar 730, the user may quickly determine that August 20-September 19 fall under the continuous protection parameter, July 21-August 19 fall under the daily protection parameter, and July 5, 12, and 19 are days when the weekly protection parameter applies. The calendar 730 may also show the dates when manual snapshots and/or transactional logs were captured of the source database (e.g., on June 7, July 13, August 19). Further, upon selecting a particular date, the user may view additional details of available snapshots and transactional logs for that date from which a clone may be created. For example, in FIG. 7A, August 21 is shown as selected. Thus, in a display portion 735, a time scale shows the available snapshots/transactional logs. Since August 21 falls under the continuous protection parameter, the user may select any time on the time scale to create a clone of the source database. If for example July 25 is selected by the user, the display portion 735 may highlight the time on the time scale at which the daily snapshot was captured (as identified from the protection schedule) and which the user may be able to select to create a clone from. Thus, the body 710 of the dashboard 700 provides a user friendly, visual, and intuitive interface for easily and quickly determining how the source database is protected and the level of protection that is available to that source database on any given day.

To clone the source database, the user may select the clone option 725A. Upon selecting the clone option 725A, the database protection system instance and particularly the clone management system of the source database initiates the cloning process. The cloning process may include three distinct operations: a time operation to identify whether the user desires to create the clone based on an available snapshot or to a point in time, a server operation to either create a new target database VM to house the clone of the source database or select a previously created target database VM, and a database operation to create the clone of the source database on the target database VM. Selecting the clone option 725A triggers the time operation by displaying a user interface 740 shown in FIG. 7B.

The user interface 740 solicits a clone name 740A, a date from a calendar 740B from which the clone is desired, and one of a point in time option 740C or snapshot option 740D. If the user desires to clone the source database to a point in time, the user may select the point in time option 740C and if the user desires to create the clone from an available snapshot, the user may select the snapshot option 740D. Upon providing the information requested in the user interface 740, the user may interact with (e.g., click on) a next button 740E, which opens user interface 745 of FIG. 7C. The dialog box 745 is shown for a point in time selection. Thus, the user interface 745 may solicit the exact time from which the clone is to be created. The user interface 745 may display the times that are available for the user to select for the point in time option. Specifically, the user interface 745 may display a time scale 745A, which may include an activated slot from which the user may pick a time and an inactivated slot that is unavailable to the user. For example, the time scale 745A shows an activated slot 745B and an inactivated slot 745C. The user may pick (e.g., by interacting with the time scale 745A or by entering the time in box 745D) a time from the activated slot 745B for creating the clone. For example, if the user selects 5:00 from the activated slot 745B, the corresponding clone management system is configured to create a clone based on the state of the source database at 5:00.

It is to be understood that the activated slot 745B corresponds to the protection parameter of the SLA and the protection schedule. For example, if the date that the user selected on the calendar 740B falls under the daily protection parameter and the protection schedule indicates that the daily snapshot is captured at 11:00 AM, in some embodiments, the user may be able to only select 11:00 AM for the clone. In other embodiments, the user may still be allowed to select times other than 11:00 AM as well. However, since only a daily snapshot is available for that date, the clone may be based on the daily snapshot of 11:00 AM.

If the user selects the snapshot option 740D in FIG. 7B, the user interface 745 may look somewhat different and may present options to allow the user to select one or more available snapshots to create a clone from. Upon selecting the point in time or the available snapshot, the user may interact with a next button 745E to display user interface 750 of FIG. 7D. The user interface 750 allows the user to either create a new target database VM 750A on the target database storage (e.g., the target database storage 655) or select an existing target database VM 750B. To create a new target database VM, the database protection system instance may solicit the target database VM name and one or more profiles (e.g., software profile, compute profile, network profile, database parameter profile), and any other desired or required information from the user. In some embodiments, one or more profiles may be same as that of the source database VM, while in other embodiments, the one or more profiles may vary from those of the source database VM. If the user selects the existing target database VM 750B, the user interface 750 may display a list of previously created target database VMs for the source database. In some embodiments, multiple target database VMs may be created for a particular source database. Upon providing the target database VM information, the user may interact with a next button 750C to display a user interface 755 of FIG. 7E.

In the user interface 755, the user may specify details of the cloned database. For example, the database protection system instance may solicit a name 755A of the cloned database, a password 755B if desired, and any other information that is desired or needed. Upon interacting with a clone button 755C, the database protection system instance creates the clone of the source database based upon the inputs received from the user in FIGS. 7A-7D. Interacting with the clone button 755C may display a user interface 760 of FIG. 7F, which shows the status of the clone. The database protection system instance may retrieve the snapshot(s) and/or the transactional logs and create the clone therefrom. For the point in time option, the database protection system instance may use both snapshots and transactional logs to create the cloned database, while for the available snapshot option, the database protection system instance may use only the available snapshot. The database protection system instance may also create a new target database VM (if a new target database VM is selected by the user). Once the cloned database is created, the cloned database may be displayed within the dashboard 700. Thus, the dashboard 700 provides an easy and convenient mechanism to clone source databases.

Turning now to FIG. 8 and referring to FIG. 8 in conjunction with FIGS. 6 and 7A-7F, an example flowchart outlining operations of a process 800 is shown, in accordance with some embodiments of the present disclosure. The process 800 may include additional, other, or different operations depending upon the embodiment. The process 800 may be used to create a cloned database from a source database. The process 800 may be implemented by the clone management systems 635 of the database protection system instances 630. The process 800 starts at operation 805 with the database protection system instances 630 receiving a user request for creating a clone. As discussed in FIG. 7A, the user may request creation of a clone of a source database via the dashboard 700. Upon receiving the user request, the database protection system instances 630 corresponding to the source database being clones is activated. The activated one of the database protection system instances 630 receives selection from the user of creating the clone from either a point in time or from an available snapshot. If the user selects the point in time option, the process 800 proceeds to operation 810. At the operation 810, the activated one of the database protection system instances 630 presents user interface, via the dashboard 700, to the user to receive selection of a specific time at which the clone is to be created. The clone is created based on the state of the source database at that specific time. At operation 815, the activated one of the database protection system instances 630 retrieves the snapshot corresponding to that specific time or the snapshot that is available closest to that specific time.

At operation 820, the activated one of the database protection system instances 630 retrieves any transactional logs that may be needed. For example, if the snapshot that is retrieved at the operation 815 is captured at the specific time selected by the user at the operation 810, then the source database may be cloned from the snapshot of the operation 815. However, if the snapshot of the operation 815 is created before or after the specific time selected by the user, then one or more transactional logs may exist between the time the snapshot is captured and the specific time. For example, if the specific time is 11:00 AM and the closest snapshot to 11:00 AM is from 10:00 AM, the database protection system instance 630 may determine if there are transactional logs available between 10:00 AM and 11:00 AM. The database protection system instance 630 may retrieve any transactional logs that may be available. If no transactional logs are available between 10:00 AM and 11:00 AM, the database protection system instance 630 may create the clone from the snapshot of 10:00 AM. Thus, at the operation 820, the activated one of the database protection system instances 630 determines if a transactional log is needed or exists, and retrieves those transactional log(s).

Additionally, at operation 825, the activated one of the database protection system instance 630 receives selection for a target database VM from the user. As indicated above, the user may either create a new target database VM or use an existing target database VM for storing the cloned database. If the activated one of the database protection system instances 630 receives selection for creating a new target database VM from the user, the database protection system instance may solicit information (e.g., name, profiles, etc.) from the user to create the target database VM. The target database VM may be associated with the target database storage. Alternatively, if the user desires to use an existing target database VM, the activated one of the database protection system instance 630 may present a list of existing target database VMs created previously for the source database. The user may select one of the existing target database VMs from the list. At operation 830, the activated one of the database protection system instances 630 creates the cloned database from the snapshot of the operation 815 and any transactional logs of the operation 820. The database protection system instances 630 stores the cloned database, at operation 835, on the target database VM, and the process 800 ends at operation 840.

If at the operation 805, the user selects the option of creating a clone from an available snapshot, the process 800 proceeds to operation 845. At the operation 845, the activated one of the database protection system instances 630 solicits the user to select the snapshot from which the clone is to be created. Upon receiving the user's selection of the available snapshot, at operation 850, the activated one of the database protection system instance 630 retrieves that snapshot. Before, after, or along with retrieving the snapshot, at the operation 825, the database protection system instance 630 may either create a new target database VM or identify an existing target database VM to use. At the operations 830 and 835, the database protection system instance 630 creates the clone of the source database and stores the cloned database on the target database VM. Again, the process 800 ends at the operation 840.

Returning back to FIG. 6, the cloned databases 660 of the source databases 650 are created from snapshots and transactional logs. Thus, to be able to create the cloned databases 660, snapshots and transactional logs are needed of the source databases 650. The snapshots and transactional logs may be captured via the snapshot/log capturing systems 640. The snapshot/log capturing systems 640 may be configured with the protection schedule and the SLA that are defined by the user when the source databases 650 are created or registered with the database system 600. The protection schedule defines, among other things, the frequency of capturing snapshots and transactional logs each day. Thus, based upon the protection schedule, the snapshot/log capturing systems 640 may instruct a data manager of the source databases 650 to capture snapshots and transactional logs automatically. As discussed above, an instance of a data manager may be associated with each source database that is created on the source database storage 645. For example, the source database 650A may be associated with a database manager 665A, the source database 650B may be associated with a data manager 665B, and the source database 650N may be associated with a database manager 665N. The database managers 665A-665N are collectively referred to herein as database managers 665. Although not shown, in some embodiments, the cloned databases 660 may each be associate with a database manager as well.

The database managers 665 are configured to capture the snapshots and the transactional logs upon instruction from the snapshot/log capturing systems 640. The database managers 665 may include an agent that captures the snapshots and the transactional logs based on the protection schedule received from the snapshot/log capturing systems 640. Thus, the database manager 665A may include an agent 670A, the database manager 665B may include an agent 670B, and the database manager 665N may include an agent 670N. The agents 670A-670N are collectively referred to herein as agents 670. Each of the agents 670 is an autonomous software program that is configured for performing one or more specific and approved operations. For example, each of the agents 670 may be configured to capture snapshots and transactional logs based upon the protection schedule, and store the captured snapshots and transactional logs in a repository associated therewith. The clone management systems 635 may retrieve the snapshots and transactional logs from the repositories when creating a clone of the source databases 650. For example, the agent 670A may be configured to store the captured snapshots and transactional logs in a repository 675A that is configured for the source database 650A, the agent 670B may be configured to store the captured snapshots and transactional logs in a repository 675B that is configured for the source database 650B, and the agent 670N may be configured to store the captured snapshots and transactional logs in a repository 675N that is configured for the source database 650N. The repositories 675A-675N are collectively referred to herein as repositories 675.

For example, if the protection schedule specifies capturing 2 snapshot every day and capturing a transactional log every 2 hours for the source database 650A, the agent 670A may capture 2 snapshots of the source database 650A and a transactional log every 2 hours such that in a 24-hour period, the agent captures 2 snapshots and 12 transactional logs. Further, if the continuous protection parameter in the SLA specifies a continuous protection of 30 days, the agent 670A may be configured to save all snapshots and transactional logs captured in the previous 30 days (not including the current day). Thereafter, the agent 670A may purge (e.g., delete) some of the snapshots and transactional logs based upon the protection parameters defined in the SLA level. For example, if the SLA level specifies a daily protection parameter of 30 days after the duration of the continuous protection parameter expires, the agent 670A may be configured to delete all but one snapshot that were captured before the previous 30 days, as well as delete all the transaction logs captured before the previous 30 days. The snapshot that is saved as the daily snapshot may be the snapshot that is closest to the daily snapshot time specified in the protection schedule. For example, if the time specified in the protection schedule is 11:00 AM for the daily snapshot, the snapshot that is captured at 11:00 AM or closest to 11:00 AM is saved and all other snapshots captured on that day are deleted. Thus, the agent 670A is configured to capture and manage snapshots and transactional logs.

Referring to FIGS. 9A-9G in conjunction with FIG. 6, an example flow diagram outlining operations of how an agent (e.g., the agents 670) of a database (e.g., the source databases 650) may capture, store, and purge snapshots and transactional logs based upon the protection schedule and protection parameters defined in the SLA level is shown, in accordance with some embodiments of the present disclosure. Simply for purposes of explanation, FIGS. 9A-9G show the flow for an SLA that requires a continuous protection of 7 days and a daily protection thereafter for 7 days. Thus, the SLA defines the continuous protection parameter as 7 days and the daily protection parameter as 7 days. Further, FIGS. 9A-9G are based on a protection schedule that specifies capturing 1 snapshot every day and 3 transactional logs every day. It is to be understood that the SLA definitions and the protection schedule above is only an example and not intended to be limiting in any way.

FIG. 9A shows the contents of a database 900 on a first day of the continuous 7 days. Since the protection schedule specifies capturing 1 snapshot every day, on the first day, the agent associated with the database 900 captures a snapshot 905. The time of the day at which the snapshot 905 is captured may either be defined in the protection schedule or may be pre-defined within the agent capturing the snapshot. Additionally, as shown in FIG. 9B, on the first day, the agent associated with the database 900 also captures 3 transactional logs (e.g., one transactional log every 8 hours) 910. On the second day, as shown in FIG. 9C, the agent associated with the database 900 captures another snapshot 915 and 3 transactional logs 920 shown in FIG. 9D. The agent associated with the database 900 continues to capture snapshots and transactional logs for 7 days to satisfy the continuous protection parameter and provide continuous protection for 7 days as defined in the SLA level. Thus, as shown in FIG. 9D, by the end of the seventh day, the agent associated with the database 900 has captured the snapshots 900, 915, snapshots 925A-925E, the transactional logs 910, 920, and 930A-930E. On the eighth and following days, the agent associated with the database 900 continues to capture snapshots (e.g., snapshot 935) and 3 transactional logs 940 shown in FIG. 9E.

However, since the SLA requires 7 days of continuous protection, after the 7 days, the continuous protection is not required and the agent may purge some of the captured snapshots and transactional logs, again based on the definitions in the SLA. As indicated above, the SLA of FIGS. 9A-9G defines a daily protection parameter of 7 days for daily protection after the expiration of the 7 days of continuous protection. Thus, on the ninth day, the snapshot 905 captured on the first day is greater than 7 days old. Since only one snapshot is captured every day, the agent associated with the database 900 maintains the snapshot as the daily snapshot. If multiple snapshots are captured each day, the agent associated with the database 900 may delete all snapshots except one. Further, since the daily protection parameter provides guarantee of a daily snapshot, the agent may delete all of the transactional logs that were captured that day. Therefore, as shown in FIGS. 9E and 9F, on the ninth day, the snapshot 905 may continue to be stored as the daily snapshot but the transactional logs 910 may be deleted. Further, on the ninth day, the agent associated with the database 900 captures another snapshot 945 to continue to provide a continuous protection for the past 7 days.

Similarly, on each day, from days 10-14, the agent associated with the database 900 continues to delete the transactional logs that are older than 7 days, and capture a new snapshot and 3 transactional logs (e.g., snapshots 950A-950E and transactional logs 955A-955E shown in FIG. 9G). Thus, the agent associated with the database 900 continues to capture snapshots and transactional logs based upon the SLA level and the protection schedule, and deletes some of the snapshots and transactional logs that are no longer required to satisfy the SLA level.

Snapshots of a source database may be captured by creating a snapshot of the source database VM and a snapshot of the source database itself. Specifically, a snapshot may be an image/copy of the location of the storage files associated with the virtual disks of the source database and an image/copy of the location of the configuration files associated with the source database VM. The virtual disk(s) on which the source database is stored may be composed of or divided into one or more memory blocks. The snapshot/log capturing systems 640 may capture images or copies of the memory blocks for capturing snapshots. A copy of the memory blocks may be made by identifying the memory pointer (e.g., location) assigned to each memory block and copying the memory pointer to a repository (e.g., the repositories 675). During a first snapshot of the memory blocks, the contents of all the memory blocks may be copied to the repositories 675. After the first snapshot is captured, transactional logs may be captured based upon the protection schedule to record all transactions or changes in the source database after the capture of the first snapshot. Capturing a transactional log may be referred to herein as a log catch up operation.

For example, say the protection schedule defines capturing 2 snapshots each day and 2 transactional logs between the 2 snapshot captures. If the source database includes 1000 memory blocks, the first snapshot creates copies of all the 1000 memory blocks. Capturing a snapshot involves pausing the source database such that no user operations are performed while the source database is being snapshotted, creating copies of the memory blocks (and other information such as the configuration file of the source database VM, etc.), and unpausing the source database. Since snapshots temporarily halt operation of the source database, taking frequent snapshots of the source database is not practical or desirable. However, to accurately capture the state of the source database in between two snapshot captures and allow creation of cloned databases to satisfy the SLA (e.g., the continuous protection parameter), transactional logs may be captured between two snapshot captures. The frequency of capturing transactional logs may be higher than the frequency of capturing the snapshots. Thus, for example and continuing the example above, if after capturing the first snapshot, 4 out of the 1000 memory blocks of the source database have changed (e.g., due to data being updated, new data being added, etc.), the agents 670 create a first transactional log based upon the protection schedule. The first transactional log may reflect that the 4 blocks have changed since the last snapshot capture. Specifically, the first transactional log may include memory pointers to the 4 memory blocks that have changed. Thus, instead of copying all of the 1000 memory blocks, the first transactional log only copies the changes since the last snapshot capture, thereby saving space and time. Similarly, based upon the protection schedule, the agents 670 may capture a second transactional log after the first transactional log. The second transactional log may determine which memory blocks have changes since the first snapshot capture.

For example, if the agents 670 determine that 6 memory blocks have changed since the first snapshot capture, the second transactional log may include memory pointers back to the first snapshot indicating which 6 of the memory blocks have changed. The 6 memory blocks that changed at the time of capturing the second transactional log may or may not include the 4 memory blocks that changed at the time of capturing the first transactional log. Thus, each transactional log that is captured identifies the memory blocks that have changed since the previous snapshot capture and include memory pointers to those changed memory blocks. When the source database is cloned, say to a state when the second transactional log is captured, the associated one of the clone management systems 635 may recreate the source database from the first snapshot and the second transactional log. Specifically, the associated one of the clone management systems 635 may determine (e.g., from the memory pointers in the second transactional log) which particular memory blocks have changed from the first snapshot. In the example above, the second transactional log includes memory pointers of the 6 memory blocks that have changed since the first snapshot capture. Thus, the agents 670 may create the cloned based on the 994 memory blocks from the first snapshot that have not changed plus the 6 memory blocks in the second transactional log that have changed. Thus, the cloned database reflects an accurate state of the source database at the time of the second transactional log capture.

Further, and continuing with the example above of capturing 2 snapshots and 2 transactional logs each day, the agents 670 may capture a second snapshot based upon the protection schedule. In some embodiments, the second snapshot may be a copy of all the memory blocks (e.g., all 1000 memory blocks in the example above) again and transactional logs that are captured after the second snapshot may identify changes in the memory blocks relative to the second snapshot. Thus, any changes made between the capture of the first snapshot and the capture of the second snapshot are reflected in the second snapshot. In other embodiments, the second snapshot may also be an incremental snapshot that reflects only which memory blocks have changed since the first snapshot capture. Thus, the second snapshot in such cases may take less time to create, as well as less space to store. The subsequent transactional logs may continue to make pointers to the first snapshot to reflect the memory blocks that change.

Advantageously, the snapshot and transactional log capturing efficiently only copies changes in the memory blocks. Furthermore, all transactions are recorded using transaction logs such that when a clone is created, the source database may be recovered based on both the snapshots and the transaction logs to any desired state. Further, since capturing a transactional log does not require pausing the source database, the transactional logs may be captured in background while the source database is operating, and the transactional logs may be captured at a greater frequency than the snapshots. To capture a transactional log, the agents 670 maintain a small staging disk. The staging disk may be part of the repositories 675 or may be separately provisioned from those repositories. The staging disk may be dedicated or shared amongst the various source databases 650 and may be used to temporarily store the transactional logs. The agents 670 may sweep (e.g., collects) the transactional logs from the source database to the staging disk based upon the protection schedule. From the staging disk, the agents 670 may start the log catch up operation to move the transactional logs from the staging disk to the repositories 675. Thus, based upon a combination of snapshots and transactional logs, the state of the source database may be effectively and accurately replicated. While the snapshots and transactional logs may be automatically captured based upon the protection schedule, in some embodiments, the database engine 605 may allow the users to manually capture snapshots and transactional logs. Such an operation may be particularly useful if the user desires a state that falls between the capture of two snapshots and transactional logs.

Referring still to FIG. 6, the database storage system 620 may also include an external database manager 680. The source databases 650 that are created within the database system 600 are already configured to be snapshotted. However, databases that were created outside of the database system 600 and registered with the database system may not have been configured to be snapshotted. Thus, such databases need to be reconfigured to be able be snapshotted and protected by the database system 600. The reconfiguration may be part of the registration process or performed after those databases have been registered. To reconfigure the externally created databases, a process 1000 of FIG. 10 may be used. Referring to FIG. 10 in conjunction with FIG. 6, a flowchart outlining the operations of the process 100 is shown, in accordance with some embodiments of the present disclosure. The process 1000 may include other, additional, or fewer operations depending upon the particular embodiment. The process 1000 may be implemented by the database engine 605.

The process 1000 starts at operation 1005 and at operation 1010, a complete back up of the external database is made by the external database manager 680. The complete backup includes a complete copy of the external database. In other words, the actual data of the database is copied when creating a back-up. Knowledge about the structure of the underlying storage (e.g., the virtual disks) of a database is not needed when a back-up is created. In contrast, snapshotting requires knowledge of the underlying storage (e.g., virtual disks) since no actual copy of the data is made. Rather, when a snapshot is captured, a copy of the location of the virtual disk where the data is stored is made. Thus, to configure the external database for capturing snapshots and transactional logs, the external database is backed up to a storage disk (e.g., virtual disk), the structure of which is known to the database engine 605. The back-up copy may be considered the source database for purposes of protection and may be part of the source database storage 645. Further, an instance of a database manager may be associated with the back-up copy to create clones from the back-up copy.

In some embodiments, the operation 1010 may be performed as part of the registration process when the external database is registered with the database system 600. In other embodiments, the operation 1010 may be performed after the registration process. Since the back-up of the external database is to a known structure of the storage disk, snapshots and transactional logs may be created from the back-up copy. Thus, at operation 1015, snapshots and transactional logs may be captured of the external database from the back-up copy. The process of capturing snapshots and transactional logs from the back-up copy is the same as that of a database created internally within the database system 600. The snapshots and transactional logs may be stored within the repositories 675 and clones may be created from those snapshots or a combination of snapshots and transactional logs.

Thus, at operation 1020, upon receiving a user request to create a clone of the external database, the database manager associated with the back-up copy of the external database may create a cloned database from the back-up copy. The clone creation process is same as discussed above. The cloned database may be stored within the target database storage 655. In some embodiments, the user may desire to store the external database outside of the database system 600 or on a system that is not compatible with the database system. Thus, at operation 1025, a user may request storing the cloned database to an external location. The database engine 605 and particularly the external database manager 680 may reconfigure the cloned database to a form that is compatible with the external location and at operation 1030, send the reconfigured database to the external location. The database engine 605 may continue to make snapshots and transactional logs of the back-up copy of the operation 1010 based upon the SLA and protection schedule defined for the external database during the registration process. When the user request of the operation 1020 is received, the database engine 605 may create the clone of the external database, reconfigure the cloned database, and send it to the external location. The process 1000 ends at operation 1035.

Thus, the database system of the present disclosure is a versatile system for creating and managing databases. A variety of operations may be performed on the databases associated with the database system using a user friendly and intuitive user interface.

It is to be understood that any examples used herein are simply for purposes of explanation and are not intended to be limiting in any way. It is also to be understood that any examples used herein are simply for purposes of explanation and are not intended to be limiting in any way. Further, although the present disclosure has been discussed with respect to memory usage, in other embodiments, the teachings of the present disclosure may be applied to adjust other resources, such as power, processing capacity, etc.

The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable,” to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.” Further, unless otherwise noted, the use of the words “approximate,” “about,” “around,” “substantially,” etc., mean plus or minus ten percent.

The foregoing description of illustrative embodiments has been presented for purposes of illustration and of description. It is not intended to be exhaustive or limiting with respect to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the disclosed embodiments. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents. 

1. A method comprising: associating a protection schedule for a source database provisioned in a database management system associated with a hyperconverged infrastructure system, the protection schedule defining a frequency of capturing snapshots and a frequency of capturing transactional logs; capturing a snapshot and a transactional log for the source database based upon the frequency of capturing snapshots and the frequency of capturing transactional logs, respectively; receiving a request identifying a point in time for creating a cloned database from the source database; retrieving the snapshot and the transactional log corresponding to the point in time; and creating the cloned database by combining data from a first storage location identified in the transactional log and the data from a second storage location identified in the snapshot.
 2. The method of claim 1, further comprising: associating a Service Level Agreement (“SLA”) with the source database, wherein the SLA defines a protection parameter defining a duration for storing the snapshot and the transactional log; and deleting the transactional log upon expiration of the duration.
 3. The method of claim 2, wherein the protection parameter comprises a continuous protection parameter defining a number of days for which the source database is to be cloned to the point in time using a combination of the snapshot and the transactional log.
 4. The method of claim 2, wherein the protection parameter comprises a daily protection parameter defining a number of days for which the source database is to be cloned based on the snapshot after the duration of a continuous protection parameter expires.
 5. The method of claim 2, wherein the protection parameter comprises a weekly protection parameter defining a number of weeks for which the source database is to be cloned based on the snapshot after the duration of a continuous protection parameter and a daily protection parameter expires.
 6. The method of claim 2, wherein the protection parameter comprises a monthly protection parameter defining a number of months for which the source database is to be cloned based on the snapshot after the duration of a continuous protection parameter, a daily protection parameter, and a weekly protection parameter expires.
 7. The method of claim 2, wherein the protection parameter comprises a quarterly protection parameter defining a number of quarters for which the source database is to be cloned based on the snapshot after the duration of a continuous protection parameter, a daily protection parameter, a weekly protection parameter, and a monthly protection parameter expires.
 8. The method of claim 2, further comprising: receiving selection of one of a plurality of built-in levels of the SLA for the source database; and associating the selected one of the plurality of built-in levels of the SLA with the source database.
 9. The method of claim 1, wherein the frequency of capturing transactional logs is greater than the frequency of capturing snapshots.
 10. The method of claim 1, wherein the point in time corresponds to a time period between the capture of two snapshots.
 11. The method of claim 1, wherein the protection schedule further comprises time periods for designating at least one of a daily snapshot, a weekly snapshot, a monthly snapshot, and a quarterly snapshot.
 12. The method of claim 1, further comprising: capturing the snapshot and the transactional log of the source database from a back-up of the source database; and creating the cloned database from the snapshot and the transactional log captured from the back-up.
 13. A method comprising: receiving a request for creating a cloned database from a source database of a hyperconverged infrastructure system; presenting in response to the request, a time scale for receiving selection of a point in time for creating the cloned database; retrieving a snapshot and a transactional log of the source database previously captured corresponding to the point in time; and creating the cloned database by combining data in a first storage location identified in the transactional log and the data in a second storage location identified in the snapshot; performing an operation on the cloned database in response to an operation request received via the dashboard.
 14. The method of claim 13, further comprising creating the cloned database on a target database virtual machine.
 15. The method of claim 13, wherein at least a subset of operations that can be performed on the source database can also be performed on the cloned database.
 16. The method of claim 13, further comprising: creating a new target database virtual machine; and associating the cloned database with the new target database virtual machine.
 17. The method of claim 13, further comprising creating an additional cloned database from the source database.
 18. A database management system comprising: a dashboard associated with a hyperconverged infrastructure system; a database storage system for storing a source database and a cloned database; and a database engine for receiving input from and providing output to the dashboard, the database engine having programmed instructions that when executed cause the database engine to: receive a request via the dashboard for creating the cloned database; present via the dashboard and in response to the request, a time scale to receive selection of a point in time; retrieve a snapshot and a transactional log of the source database previously captured corresponding to the point in time; and create the cloned database by combining data in storage locations identified in the transactional log and the data in remaining storage locations identified in the snapshot; and perform an operation on the cloned database in response to an operation request received via the dashboard.
 19. The database system of claim 18, wherein the source database is associated with an agent, and wherein the agent captures the snapshot and the transactional log based upon a frequency of capturing snapshots and a frequency of capturing transactional logs, respectively, in a protection schedule.
 20. The database system of claim 18, wherein the source database performs a first set of operations and the cloned database performs a second set of operations simultaneously with the first set of operations. 